Passive data collection from third-party channel applications

ABSTRACT

Disclosed herein are system, method, and computer-readable storage-medium embodiments for implementing passive data collection from third-party channel applications. An embodiment includes running a channel application of a first layer of an operating system, and receiving an application programming interface (API) call, from the channel application, for a module of a second layer of the operating system. The module may be a non-video playback module that includes graphic rendering logic, for example. Some embodiments may further include intercepting metadata sent to the module, determining identifying information of a content instance based on the intercepted metadata, and storing the determined identifying information of the content instance.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/812,621, filed Mar. 9, 2020, which is a continuation of U.S. patentapplication Ser. No. 16/524,969, filed Jul. 29, 2019, now abandoned,which is a continuation of U.S. patent application Ser. No. 14/536,463,filed Nov. 7, 2014, now U.S. Pat. No. 10,368,121, issued Jul. 30, 2019,all of which are herein incorporated by reference in their entireties.

FIELD

Various embodiments of the invention relate to systems and methods forcollecting information about television programs.

BACKGROUND

The number of television programs available to users have dramaticallyincreased over the years. Today there are numerous streaming servicesthat offer thousands of video on demand (VOD) programs. Even traditionalcable networks like ABC, CBS, and NBC have started their own streamingservices in their efforts to capture the users' attention and loyalty.In addition to all of the available VOD programs, there are alsonumerous broadcast programs that are available to the users.Consequently, users now face a sea of readily available programs inwhich they have to wade through in order to find something to watch. Oneway to help users discover programs to enjoy is to provide useful dataanalytics such as most watched programs, currently trending programs,number of current viewers, etc.

One of the most used methods for obtaining viewing data (i.e., what theuser is current watching) is to execute a direct query to the userdevice. However, in an open development environment, this method is notalways available due to the lack of control of third party channels.Accordingly, an alternative and accurate method is needed for collectingviewing data.

SUMMARY OF THE INVENTION

An improved data collection method/system is described herein. Themethod/system is configured to collect viewing data by using both activeand passive data collection methods. The passive data collection methodinvolves collecting and analyzing existing data sent by a channelapplication to a rendering function/engine residing on the operatingsystem of the user's device. The passive data collection methodincludes: running a channel application located on a first layer of anoperating system of a user device; receiving an application interface(API) call, from the channel application, for a graphic rendering modulelocated on a second layer of the operating system, wherein the graphicrendering module is a non-video playback module; intercepting metadatasent to the graphic rendering module; determining identifyinginformation of a content based on the intercepted metadata; and storingthe determined identifying information of the content.

The graphic rendering module may comprise graphic rendering librarycomponents residing in the runtime/layer (just below the applicationframework layer, which is below the application layer). In one aspect, agraphic rendering library component may comprise BrightScript componentssuch as roSpringboardScreen, roVideoScreen, and roImageCanvas. Inanother aspect, the graphic rendering module is a DirectFB module(direct frame buffer) or an OpenGL module.

The method further includes sending the intercepted metadata to a remoteserver and determining the identifying information of the content at theremote server. The identifying information may be a unique identifierthat uniquely identifies the content. Additionally, the method mayinclude: receiving a user selection to play the content; receiving anAPI call, from the channel application, for a multimedia playback moduleto play the selected content; receiving a data stream for the selectedcontent from a media server; and rendering one or more of the metadatasent to the graphic rendering module on a display screen using thegraphic rendering module prior to the multimedia playback module playingthe received data stream. It should be noted that a graphic renderingmodule is different from a multimedia playback module, which isconfigured to receive an adaptive data stream; decode the received datastream; and display the data stream, Whereas a graphic rendering moduleis for rendering graphics on the screen and not for decoding data streamand playing back the data stream on a display.

In one aspect, the method further comprises displaying a plurality ofcontents using a content selection user interface. Once the user selectsa content from the content selection UI, the metadata for the selectedcontent is sent to a remote server for analysis while the metadata isbeing rendered on a display screen by a graphic rendering engine. Uponreceiving the metadata, the remote server may determine the identifyinginformation of the content using the metadata. The remote server mayalso aggregate the identifying information of the content from channelapplications operating on other user devices. Additionally, theaggregated identifying information (collected by the remote server) maybe displayed on a display screen.

In yet another aspect, a non-transitory processor-readable medium havingone or more instructions operational on a client device is disclosedherein. The instructions, which when executed by a processor causes theprocessor to: run a channel application located on a first layer of anoperating system; receive an application interface (API) call, from thechannel application, for a graphic rendering module located on a secondlayer of the operating system, wherein the graphic rendering module is anon-video playback module; intercept metadata sent to the graphicrendering module; determine identifying information of a content basedon the intercepted metadata; and store the identifying information ofthe content.

In yet another aspect, a system for streaming multimedia is disclosedherein. The system includes a user device having a first memory thatretains a first set of instructions to: run a channel applicationlocated on a first layer of an operating system; receive an applicationinterface (API) call, from the channel application, for a graphicrendering module located on a second layer of the operating system,wherein the graphic rendering module is a non-video playback module;receive metadata from a media server, wherein the metadata is sent tothe graphic rendering module; send the received metadata to a remoteserver. The system also includes a first processor, at the user device,that executes the first set of instructions. Additionally, the remoteserver has a second memory that retains a second set of instructions to:determine identifying information of a content based on the interceptedmetadata; and store the identifying information. Finally, the systemincludes a second processor, at the remote server, that executes thesecond set of instructions.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing summary, as well as the following detailed description, isbetter understood when read in conjunction with the accompanyingdrawings. The accompanying drawings, which are incorporated herein andform part of the specification, illustrate a plurality of embodimentsand, together with the description, further serve to explain theprinciples involved and to enable a person skilled in the relevantart(s) to make and use the disclosed technologies.

FIG. 1 illustrates an exemplary streaming environment.

FIG. 2 illustrates an exemplary operating system in accordance to anaspect of the disclosure.

FIGS. 3-4 illustrate exemplary user interfaces of systems for collectingviewing data and determining a total view count in accordance to anaspect of the disclosure.

FIG. 5 illustrates an exemplary operating system in accordance to anaspect of the disclosure.

FIGS. 6-7 illustrates exemplary processes for collecting viewing dataand determining a total view count in accordance to an aspect of thedisclosure.

FIGS. 8-9 illustrate exemplary user communication processes of systemsfor collecting viewing data and determining a total view count inaccordance to an aspect of the disclosure.

FIG. 10 illustrates an exemplary user interface.

FIG. 11 is a block diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system that mayexploit the systems and methods of FIGS. 3-10 in accordance to an aspectof the disclosure.

FIG. 12 is a block diagram of exemplary software modules implemented byvarious aspects of the disclosure.

DETAILED DESCRIPTION

In the following description numerous specific details are set forth inorder to provide a thorough understanding of the invention. However, oneskilled in the art would recognize that the invention might be practicedwithout these specific details. In other instances, well known methods,procedures, and/or components have not been described in detail so asnot to unnecessarily obscure aspects of the invention.

The word “exemplary” is used herein to mean “serving as an example,instance, or illustration.” Any implementation or aspect describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other aspects of the disclosure. Likewise, the term“aspects” does not require that all aspects of the disclosure includethe discussed feature, advantage or mode of operation.

Overview

Today, more and more people are eliminating their cable and satelliteservices altogether to go with streaming solutions such as the Rokustreaming player. The streaming option is attractive to many people fora variety of reasons including it being a cheaper alternative tocable/satellite television and the instant accessibility to thousands ofprograms across many different streaming platforms and providers such asRoku® channels, Netflix®, HBO GO®, and M-GO for example. Additionally,the required investment on hardware is minimal and sometime even free asthe streaming software application is preloaded onto many devices.

FIG. 1 illustrates an exemplary streaming environment 100 common to moststreaming systems. As shown in FIG. 1 , environment 100 includes atelevision 110 such as a LED flat screen TV, the Internet 120, a userdevice 130 such as a mobile phone or tablet, a display device 140,streaming client devices 150 a-b, and a plurality of servers 160A-160N.Television 110 may be an Internet enabled smart TV having preloadedstreaming applications such as the Roku streaming application or RokuTV. For example, TCL® and Hisense® brands televisions include Roku TVright out of the box, thus enabling users to immediately stream programsfrom a selection of more than 1000+ channels straight to theirtelevisions without the need to purchase any additional hardware orsoftware. Once the streaming application (e.g., Roku TV) is executed, itcommunicates with one or more content servers 160 a-160 n via Internet120 to request and receive streaming program/content for display ontelevision 110.

User device 130 may be a smartphone, a tablet, or any other suitablemobile devices with the ability to access the Internet or broadbandwireless such as 4G LTE, 5G, or any other suitable wirelesscommunication standard. User device 130 may include a streamingapplication such as Roku mobile App (not shown) to enable it to streamcontents from one or more servers 160 a-n via the Internet to userdevice 130, television 110, or display device 140.

Streaming contents may also be delivered to a display device such asdisplay device 140 using a streaming player 150 a or streaming stick 150b. Each of streaming player 150 a and streaming stick 150 b is connectedto an audio/video input (e.g., HDMI, MHL) of display device 140. In thisset up, all of the software applications needed for streaming and videodecoding reside on streaming player 150 a or streaming stick 150 b. Anexemplary streaming player 150 a is the Roku 3, and an exemplarystreaming stick 150 b is the Roku Streaming Stick.

Environment 100 may also include a traditional cable or satelliteset-top-box (STB) 160 configured to stream multimedia from the Internet.This is often referred to as over the top (OTT) content delivery becausethe main mode of content delivery for STB 160 is accomplished via cableor satellite. Most cable and satellite providers (e.g., DISH andDirecTV) provide some form of data analytic reports such as most watchedprograms and what's hot feature to users by configuring the STBs tocontinuously collect and send back data on the state of the STBs.However, these STBs can only collect programming data (i.e., currentlywatched program) while the user is running the native program guide(i.e., the interactive/electronic program guide (EPG)) and only forbroadcast programming (not for OTT content nor 3^(rd) partyapplications). Additionally, traditional STBs are only set up to collectcontent data by directly querying the STBs for viewing information.

Passive Data Collection

An improved data collection system is described herein. The system isconfigured to collect viewing data by using both active and passive datacollection techniques. Viewing data may include current channel,currently watched content, previously selected channel, etc. Active datacollection involves directly querying the user's device or the operatingsystem of the user's device for viewing data. However, the direct querymethod is not always possible, especially in an open developmentenvironment with thousands of 3^(rd) party channel applications. Passivedata collection involves collecting and using existing data sent by achannel application to a rendering function/engine residing on theoperating system of the user's device.

FIG. 2 illustrates an exemplary operating system 210 of a user device.Operating system 210 includes several operating system layers. The topmost layer is an application layer 220. Operating system 210 alsoincludes a middleware layer 230 and an operating system core layer 240.A hardware layer 250 of user device 200 sits below core layer 240.Application layer 220 is typically where all channel applications areinstalled.

To perform various functions such as video playback or graphicrendering, channel applications (222-228) are configured to make APIcalls to various libraries and services residing in middleware layer 230and sometime core layer 240. The multilayered architecture is to provideproper isolation of each application in application layer 220.Application isolation is typically achieved by assigning each runningapplication to a virtual operating environment or machine where allrunning processes is confined within the assigned virtual machine. Thisprocess is also referred to as sandboxing. The sandboxing processprotects the application's processes and data by preventing anotherconcurrently running application from accessing to the application'sdata and processes.

As shown in FIG. 2 , middleware layer 230 includes library and servicessuch as system services 232, core libraries 234, a process manager 236,and other services (not shown). Core layer 240 includes an OS kernel 242which contains drivers for controlling various devices at a hardwarelayer 250 such as display screen, speakers, and wireless communicationservices (e.g., WiFi, near field communication, etc.).

To facilitate the description of the passive data collection method,FIGS. 3-4 will be discussed in conjunction with FIG. 2 . FIG. 3illustrates an exemplary content option UI (user interface) 300 thatincludes a provider indication area 310, a content graphic area 320, acontent information area 330, a content title area 340, a main titlearea 350, and a menu selection area 360. Provider indication area 310indicates the name or source of the channel such as Showtime Anytime®.Content graphic area 320 displays relevant box art or graphicrepresenting the content. Content information area 330 providesadditional description about the content represented by graphic area320.

Content title 340 provides the name of the movie or episode of thecontent. Main title area 350 provides the series name of the series ofthe content is part of a series. Otherwise, main title area 350 andcontent title 340 may contain identical data. Menu selection area 360provides the user with options/actions the user may take includingplaying the content, add to future watch list, view credits andadvisories, and browse all episode relating to the series.

Content option UI 300 may be a component of core libraries 234. Contentoption UI 300 may be generated by any channel application, running onapplication layer 220, using an API call to library 234 for the contentoption UI library component (not shown). In one aspect, when a channelapplication makes an API call to generate content option UI 300, itautomatically forwards the metadata of fields 310-350 to the contentoption UI library component. Alternatively, the content option UIlibrary component may send a request for data to the channel applicationfor one or more fields 310-350.

Although the content option UI library component is described to be partof core libraries 234 residing in middleware layer 230, it may span morethan one modules system services 232 and libraries 234) on layer 230.Additionally, content option UI library component may span multiplelayers of operating system 210 (i.e., middleware layer 230 and corelayer 240). Once the content option UI library component is called, thedata received from the channel application (cyan metadata) for fields310-350 is sent to a home server (not shown) for storage and analysis.The home server is the default server to which all usage and behavioraldata collected by operating system 210 are sent, and it may be remotelylocated.

Upon receipt of the metadata for fields 310-350, the home serveranalyzes the metadata and matches it with a known content. This may bedone by analyzing the metadata for content title area 340 and main titlearea 350 and corresponding the metadata to a known content and thecontent identifier. The home server then stores the content identifieralong with the user's profile. By associating the content identifierwith the user's profile, the system can form a better entertainmentprofile for the user. Additionally, various viewing statistics can begenerated once the content identifier has been identified. Some examplesof viewing statistics that could be generated are total view count(across all platforms and devices); most watched programs; most watchedprograms by age group, sex, geographic location, etc.

In one aspect, the home server collects channel metadata from all activeuser devices and determines the content identifier for each respectivedevice. The home server then aggregates the content identifiers andgenerates a total view count for each content. Active user devices, inthis context, include various devices across multiple platforms such astelevision, streaming player, streaming stick, mobile devices, etc. Thehome server may also send the total view count back to the user devicefor display. The user device may display the view count during theplayback of the content. For example, the user device may be streamingseason 2, episode 3 of Breaking Bad, during the streaming of thecontent, the user device receives the view count data (for S02E03)across all devices and platforms from the home server and displays it tothe user. For example,

FIG. 4 illustrates a buffering UI 400 that includes a title area 410 anda buffering status indication area 420. Buffering UI 400 may be launchedby a channel application to inform the user that the selected content isbuffering and is starting momentarily. In one aspect, buffering UI 400is generated by a graphic rendering module, which may be a component ofsystem services 232, libraries 234, or both. For example, buffering UT400 may be generated by a QLabel function, which is a widget of the Qt®platform. On a high level, Qt is a cross-platform applicationdevelopment toolkit that enable developers to code once (and compile)and run on various platforms such as Windows, Android, Mac OS, andLinux.

In another aspect, buffering UI 400 may be generated by a lower layergraphic rendering module which may have one or more components residingin kernel layer 240 (including a thin layer at application layer 210 inorder to expose the API functions of the graphic rendering module). Forexample, the channel application may generate buffering UI 400 by makingAPI calls directly to a graphic rendering engine such as a DirectFB(direct frame buffer) module or an OpenGL module. When the channelapplication makes an API call to the DirectFB or the OpenGL graphicrendering module, it also passes along the metadata for title area 410,which is also forwarded to the home server. The metadata for title area410 may be automatically forward to the home server by the DirectFB orOpenGL API module. Once the home server receives the metadata for titlearea 410, it analyzes the metadata to determine a content identifierthat corresponds with the metadata.

FIG. 5 illustrates an exemplary operating system 500 in which aspects ofthe disclosure can be implemented. Operating system 500 may reside onstreaming client devices 150 a-150 b and television 110, for example.Operating system 500 includes an application shell 510, an applicationlayer 520, a BrightScript components module 530, a BrightScript enginemodule 540, a software platform layer 550, and a kernel layer 560.Kernel layer 560 sits directly on top of a hardware layer 570 to manageand interact with various hardware components such as memory, devicedrivers, security, networking services, etc.

BrightScript component module 530 and engine module 540 may be part ofthe framework and runtime layer of operating system 500. Applicationshell 510 may reside on multiple layers such as application layer 520,the framework layer, and the runtime layer. In one aspect, applicationshell 510 serves as a translation layer for communication betweenapplications, libraries components, and system resources at the kernellayer.

Application layer 520 is where 3^(rd) party channel applications residesuch as channel applications 522 and 524. At runtime, each channelapplication is assigned its own virtual machine, which operates as anindependent operating system running within host operating system 500.For example, application channel 522 operates within its own virtualmachine that is independent and separate from channel application 524,which also operates within the confine of its own virtual machine. Thevirtual machine is configured to run any application plug-in (or channelapplication) as if it is operating on top of its own physical machine.Since a channel application is required to run within the boundary ofits own virtual machine, the processes and data of the channelapplication are protected from other concurrently running channelapplications. Data cannot be shared between channel applications unlessexpress permission is granted by the user.

In one aspect, the content option UI library component described withrespect to FIG. 3 resides within BrightScript components module/layer530 and BrightScript engine 540. Examples of graphic renderingBrightScript components are roSpringboardScreen, roVideoScreen, androImageCanvas. Each of the roSpringboardScreen, roVideoScreen, androImageCanvas components requires certain metadata from the API callingchannel application in order to render the appropriate information onthe user's display. One or more of the following metadata may berequired by a graphic rendering BrightScript component: ContentType,Title, TitleSeason, Description, StreamURLs, StreamContentIDs,StreamFormat, Length, Actors, Directors, Categories, etc. It should benoted that this list is not exhaustive.

Each of the BrightScript component may be configured to automaticallyforward any metadata received from the API calling channel applicationto the home server. In essence, the metadata is intercepted or capturedfor the home server. In this way, the home server can analyze themetadata to determine the corresponding content identifier, which is aunique identifier assigned to each television episode, movie, clip, etc.

FIG. 6 illustrates an exemplary process 600 for collecting viewing dataand implicitly determining what the user is currently watching inaccordance to one aspect of the disclosure. Process 600 starts at 602where an API call is received by a graphic rendering module. In oneaspect, the graphic rendering module is the content option UI librarycomponent as described in FIG. 2 . In another aspect, the graphicrendering module is a graphic rendering engine such as a DirectFB engineor an OpenGL engine. At 604, the metadata sent to the graphic renderingengine by the channel application are intercepted and sent to the homeserver for analysis. At 606, the identifying information, which may be aunique content identifier, is determined from the intercepted metadata.In one aspect, the intercepted metadata is analyzed locally at the userdevice to determine the unique content identifier of the content beingreferenced by content option UI 300 or buffering UI 400. At 608, theidentifying information is stored and used to generate various viewingstatistics such as total view count in real-time, all time total viewcount, view count by platform, etc.

FIG. 7 illustrates an exemplary process 700 for collecting viewing datain accordance to one aspect of the disclosure. Process 700 starts at 702where a channel application is executed. An example of a channelapplication is HBO GO® or M-GO. At 704, the channel application makes anAPI call to the graphic rendering module in response to the userselection of a content. FIGS. 3-4 are examples of UI being rendered byone of the graphic rendering modules after a user makes a contentselection. Whether content option UI 300 or buffering UI 400 is rendereddepends on the UI architecture of the channel application. In oneaspect, when the user makes a selection of a content (from a pluralityof contents), content option UI 300 is immediately rendered to providethe user with a variety of options as indicated by option area 360. Inone aspect, buffering UI 400 is rendered after the user selects “Play”in option area 360 (at 710, which will be further discussed below).

In one aspect, buffering UI 400 is rendered immediately after the userselects the content from a plurality of contents in a content selectionUI 1000 as shown in FIG. 10 . Referring now to FIG. 10 , whichillustrates an exemplary content selection UI 1000 that includes aprovider's indication area 1010, a list of contents in a panel format1120, a currently highlighted content 1130, and a description area 1140of highlighted content 1130. Alternatively, content selection UI 1000may be a simple list of content items from which the user can select.

Referring again to FIG. 7 , at 706, the metadata sent to the graphicrendering module is intercepted and forwarded to a remote server wherethe identifying information of the selected content is determined. Aspreviously mentioned, the identifying information may be a uniqueidentifier that identifies the exact movie or episode of the show. Forexample, an identifier determining module (not shown) is configured togenerate a unique identifier such that it would distinguish the classic1953 War of the Worlds movie from the 2005 War of the Worlds remake, andany other remake hereafter. At 710, a user selection to play the contentis received. Once this occurs, process 700 renders the metadata(intercepted at 706) and displays it in buffering UI 400. For example,if the user selects to play the 2005 War of the Worlds movie, graphicrendering module would render the title of the movie in main title area410 of buffeting UI 400 using the metadata received at 706. Only afterdisplaying buffering UI 400, the channel application would playback theselected content using an audio/video playback module. In one aspect, anaudio/video playback module is roVideoScreen-a BrightScript videoplayback component. Alternatively, the audio/video playback module isStagefright, which is a native level Android media playback engine. Itshould be noted that a channel application does not need to render boththe content option UT 300 and the buffering UI 400. The channelapplication may only render buffering UI 400 immediately after thecontent is selected from content selection UI 1000.

FIG. 8 illustrates a communication process flow 800 between variousdevices and software modules in accordance with one aspect of thedisclosure. Communication process 800 includes a user interface 810, achannel application 820, a graphic rendering module 830, a videoplayback module 840, and a home server 850. User interface 810 may bedisplayed by television 110, streaming player 150 a, or streaming stick150 b. User interface 810 may be content option UI 300 or contentselection UI 1000. At 860, a user selection of a content is made viacontent UI 300, for example. The content selection is then sent to theunderlining channel application 820 running content UI 300. At 862,channel application 820 makes an API call to graphic rendering module830. In one aspect, during the API call, channel application 820 alsosends all of the metadata relating to the selected content at 860.Alternatively, at 864, the metadata is sent to the rendering module in aseparate process.

At 866, the metadata received by rendering module 830 is sent to aremote home server 850. Home server 850 is the default server to which aplurality of user devices 130, 150 a, and 150 b send metadata forcollection and analysis. There may be multiple home servers 850 to servevarious geographic locations. Once the metadata is received by homeserver 850, the metadata is analyzed to determine the identifyinginformation of the content.

At 868, rendering module 830 renders the received metadata on thedisplay screen of the user interface. In one aspect, rendering module830 renders content option UI 300 in response to the user selection of acontent. At 870, the user selects a content to be played/streamed. Theplay command is then sent to channel application 820, which in turnmakes an API call to video playback module 840 (at 872) to playback theselected content received from a streaming server (not shown). At 874,the selected content is streamed to user interface 810 or a user'sdisplay screen.

At 876, home server 850 send data analytics results to rendering module830, which subsequently renders the data analytics results to the useron a display screen at 878. In one aspect, home server 850 aggregatesmetadata from all active user devices configured to collect data asdescribed by processes 600 and 700. For example, home server 850 maydetermine that there are 120,000 other viewers currently watching thesame content as the user. Since the user may find this form of dataanalytics to be interesting, the data analytics results may be displayedto the user as an overlay while the user is watching the streamedcontent.

It should be noted that buffering UI 400 may also be rendered byrendering module 830 just before video playback module 840 decodes thedata stream and displays the content on a display screen of userinterface 810. In this way, the user may be informed of the content'stitle and the buffering status.

FIG. 9 illustrates a communication process flow 900 between variousdevices and software modules in accordance with one aspect of thedisclosure. Process flow 900 starts at 960 when the user selection of acontent is received by channel application 820. At 962, channelapplication 820 makes an API call to rendering module 830. The metadatarelated to the selected content at 960 is also sent to rendering module830 through the API call. At 964, the metadata is sent to home server850 for storage and analysis. At 966, channel application 820 makesanother API call to video playback module 840 and instructs it to bufferand stream the selected content. At 968, prior to streaming the selectedcontent on a display screen, rendering module 830 renders the metadatareceived at 962 on the display screen. In one aspect, buffering UI 400is rendered by rendering module 830 at 968. It should be noted thatsteps 966 and 968 can be executed in reversed as long as step 968 isexecuted before step 970.

At 970, the selected content (at 960) is displayed on the display screenof user device/interface 810. At 972, home server sends the dataanalytics results to rendering module 830 for rendering as an overlaygraphic on the display screen at 974. It should be noted that theanalysis of the metadata to determine the unique identifier of theselected content may be done locally by user device 810.

Exemplary Hardware Implementation

FIG. 11 illustrates an overall system or apparatus 1100 in which thesystems, methods and apparatus of FIGS. 1-10 may be implemented. Inaccordance with various aspects of the disclosure, an element, or anyportion of an element, or any combination of elements may be implementedwith a processing system 1114 that includes one or more processingcircuits 1104. Processing circuits 1104 may include microprocessingcircuits, microcontrollers, digital signal processing circuits (DSPs),field programmable gate arrays (FPGAs), programmable logic devices(PLDs), state machines, gated logic, discrete hardware circuits, andother suitable hardware configured to perform the various functionalitydescribed throughout this disclosure. That is, the processing circuit1104, as utilized in the apparatus 1100, may be used to implement anyone or more of the processes described above and illustrated in FIGS.6-9 such as processes for collecting viewing data and determining aunique content identifier.

In the example of FIG. 11 , the processing system 1114 may beimplemented with a bus architecture, represented generally by the bus1102. The bus 1102 may include any number of interconnecting buses andbridges depending on the specific application of the processing system1114 and the overall design constraints. The bus 1102 links variouscircuits including one or more processing circuits (representedgenerally by the processing circuit 1104), the storage device 1105, anda machine-readable, processor-readable, processing circuit-readable orcomputer-readable media (represented generally by a non-transitorymachine-readable medium 1106.) The bus 1102 may also link various othercircuits such as timing sources, peripherals, voltage regulators, andpower management circuits, which are well known in the art, andtherefore, will not be described any further. The bus interface 1108provides an interface between bus 1102 and a transceiver 1110. Thetransceiver 1110 provides a means for communicating with various otherapparatus over a transmission medium. Depending upon the nature of theapparatus, a user interface 1112 (e.g., keypad, display, speaker,microphone, joystick) may also be provided.

The processing circuit 1104 is responsible for managing the bus 1102 andfor general processing, including the execution of software stored onthe machine-readable medium 1106. The software, when executed byprocessing circuit 1104, causes processing system 1114 to perform thevarious functions described herein for any particular apparatus.Machine-readable medium 1106 may also be used for storing data that ismanipulated by processing circuit 1104 when executing software.

One or more processing circuits 1104 in the processing system mayexecute software or software components. Software shall be construedbroadly to mean instructions, instruction sets, code, code segments,program code, programs, subprograms, software modules, applications,software applications, software packages, routines, subroutines,objects, executables, threads of execution, procedures, functions, etc.,whether referred to as software, firmware, middleware, microcode,hardware description language, or otherwise. A processing circuit mayperform the tasks. A code segment may represent a procedure, a function,a subprogram, a program, a routine, a subroutine, a module, a softwarepackage, a class, or any combination of instructions, data structures,or program statements. A code segment may be coupled to another codesegment or a hardware circuit by passing and/or receiving information,data, arguments, parameters, or memory or storage contents. Information,arguments, parameters, data, etc. may be passed, forwarded, ortransmitted via any suitable means including memory sharing, messagepassing, token passing, network transmission, etc.

The software may reside on machine-readable medium 1106. Themachine-readable medium 1106 may be a non-transitory machine-readablemedium. A non-transitory processing circuit-readable, machine-readableor computer-readable medium includes, by way of example, a magneticstorage device (e.g., hard disk, floppy disk, magnetic strip), anoptical disk (e.g., a compact disc (CD) or a digital versatile disc(DVD)), a smart card, a flash memory device (e.g., a card, a stick, or akey drive), RAM, ROM, a programmable ROM (PROM), an erasable PROM(EPROM), an electrically erasable PROM (EEPROM), a register, a removabledisk, a hard disk, a CD-ROM and any other suitable medium for storingsoftware and/or instructions that may be accessed and read by a machineor computer. The terms “machine-readable medium”, “computer-readablemedium”, “processing circuit-readable medium” and/or “processor-readablemedium” may include, but are not limited to, non-transitory media suchas portable or fixed storage devices, optical storage devices, andvarious other media capable of storing, containing or carryinginstructions) and/or data. Thus, the various methods described hereinmay be fully or partially implemented by instructions and/or data thatmay be stored in a “machine-readable medium,” “computer-readablemedium,” “processing circuit-readable medium” and/or “processor-readablemedium” and executed by one or more processing circuits, machines and/ordevices. The machine-readable medium may also include, by way ofexample, a carrier wave, a transmission line, and any other suitablemedium for transmitting software and/or instructions that may beaccessed and read by a computer.

The machine-readable medium 1106 may reside in the processing system1114, external to the processing system 1114, or distributed acrossmultiple entities including the processing system 1114. Themachine-readable medium 1106 may be embodied in a computer programproduct. By way of example, a computer program product may include amachine-readable medium in packaging materials. Those skilled in the artwill recognize how best to implement the described functionalitypresented throughout this disclosure depending on the particularapplication and the overall design constraints imposed on the overallsystem. For example, the machine-readable storage medium 1106 may haveone or more instructions which when executed by the processing circuit1104 causes the processing circuit to: receive, from an application, arequest to access the input data; determine a coordinate of the inputdata; determine a status of the requesting application; and grant therequest for access to the input data based on the determined coordinateand the status of the requesting application.

One or more of the components, steps, features, and/or functionsillustrated in the figures may be rearranged and/or combined into asingle component, block, feature or function or embodied in severalcomponents, steps, or functions. Additional elements, components, steps,and/or functions may also be added without departing from thedisclosure. The apparatus, devices, and/or components illustrated in theFigures may be configured to perform one or more of the methods,features, or steps described in the Figures. The algorithms describedherein may also be efficiently implemented in software and/or embeddedin hardware.

The various illustrative logical blocks, modules, circuits, elements,and/or components described in connection with the examples disclosedherein may be implemented or performed with a general purpose processingcircuit, a digital signal processing circuit (DSP), an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) or other programmable logic component, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. A generalpurpose processing circuit may be a microprocessing circuit, but in thealternative, the processing circuit may be any conventional processingcircuit, controller, microcontroller, or state machine. A processingcircuit may also be implemented as a combination of computingcomponents, e.g., a combination of a DSP and a microprocessing circuit,a number of microprocessing circuits, one or more microprocessingcircuits in conjunction with a DSP core, or any other suchconfiguration.

Note that the aspects of the present disclosure may be described hereinas a process that is depicted as a flowchart, a flow diagram, astructure diagram, or a block diagram. Although a flowchart may describethe operations as a sequential process, many of the operations can beperformed in parallel or concurrently. In addition, the order of theoperations may be re-arranged. A process is terminated when itsoperations are completed. A process may correspond to a method, afunction, a procedure, a subroutine, a subprogram, etc. When a processcorresponds to a function, its termination corresponds to a return ofthe function to the calling function or the main function.

Those of skill in the art would further appreciate that the variousillustrative logical blocks, modules, circuits, and algorithm stepsdescribed in connection with the aspects disclosed herein may beimplemented as electronic hardware, computer software, or combinationsof both. To clearly illustrate this interchangeability of hardware andsoftware, various illustrative components, blocks, modules, circuits,and steps have been described above generally in terms of theirfunctionality. Whether such functionality is implemented as hardware orsoftware depends upon the particular application and design constraintsimposed on the overall system.

The methods or algorithms described in connection with the examplesdisclosed herein may be embodied directly in hardware, in a softwaremodule executable by a processor, or in a combination of both, in theform of processing unit, programming instructions, or other directions,and may be contained in a single device or distributed across multipledevices. A software module may reside in RAM memory, flash memory, ROMmemory, EPROM memory, EEPROM memory, registers, hard disk, a removabledisk, a CD-ROM, or any other form of storage medium known in the art. Astorage medium may be coupled to the processor such that the processorcan read information from, and write information to, the storage medium.In the alternative, the storage medium may be integral to the processor.

FIG. 12 illustrates an exemplary processing circuit 1200 configured toimplement various aspects of the present disclosure. Processing circuit1200 includes an applications module 1220, a library module 1230, a dataanalysis module 1240, and a core services module 1240. Library module1230 includes graphic rendering module 1232, video playback module 1234,user interface module 1236, and an I/O module 1238. One or more ofmodules 1220-1250 contain instructions and algorithms to execute process600 of FIG. 6 , process 700 of FIG. 7 , communication process 800 ofFIG. 8 , and communication process 900 of FIG. 9 . Additionally, one ormore of modules 1220-1250 may contain instructions to generate contentoption UI 300, buffering UI 400, and content selection UI 1000.Additionally, processing circuit 1200 may include one or more functionsof processing circuit 1104.

Although not shown, processing circuit 1200 may include a memory devicethat is readable by processing circuit 1200. In one aspect, the memorydevice may be an on-chip memory device that contains all instructionsfor each of modules 1220-1250 that enable processing circuit 1200 toexecute processes 600, 700, 800, and 900 and to render user interfaces300, 400, and 1000.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of and not restrictive on the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other modifications arepossible. Those skilled, in the art will appreciate that variousadaptations and modifications of the just described preferred embodimentcan be configured without departing from the scope and spirit of theinvention. Therefore, it is to be understood that, within the scope ofthe appended claims, the invention may be practiced other than asspecifically described herein.

What is claimed is:
 1. A computer-implemented method, comprising:running, by at least one computer processor, in an environment capableof running third-party applications, a first application in a firstsandboxed virtual operating environment of a user device, wherein thefirst application comprises channel metadata unavailable to a secondapplication outside the first application; receiving a call, from thesecond application in a second sandboxed virtual operating environmentof the user device, for a module, wherein the module is a non-videoplayback module comprising graphic rendering logic; interceptingmetadata sent to the module; determining identifying information of acontent instance based on the intercepted metadata; generatingstatistics related to the content instance by analyzing the interceptedmetadata with respect to the content instance and at least one aggregatecontent identifier; forming an entertainment profile for a user of theuser device by associating the identifying information with a userprofile on the user device; and storing the determined identifyinginformation of the content instance, the statistics related to thecontent instance, the entertainment profile for the user, and a relationof the determined identifying information of the content instance to theentertainment profile for the user.
 2. The method of claim 1, furthercomprising rendering one or more of the channel metadata sent to themodule on a display screen using the module, prior to multimediaplayback of a received data stream.
 3. The method of claim 1, furthercomprising receiving a user selection of the content instance from aplurality of content instances, wherein the intercepted metadata is sentby the first application and is based on the content instance selectedby the user selection.
 4. The method of claim 1, further comprising:determining, for a plurality of other user devices, at least one othercontent identifier corresponding to the content instance, for at leastone other user device of the plurality of other user devices, to form aplurality of the other content identifiers corresponding to the contentinstance; aggregating the plurality of the other content identifierscorresponding to the content instance, to create the at least oneaggregate content identifier; and displaying the at least one aggregatecontent identifier.
 5. The method of claim 4, wherein the at least oneaggregate content identifier includes a most-watched program rankingbased at least in part on a view-count statistic.
 6. The method of claim5, wherein the most-watched program ranking is specific to a viewerdemographic.
 7. The method of claim 1, wherein the channel metadatacomprises at least one of a title of the content instance, a director, acast, or studio information, and wherein the statistics related to thecontent instance comprise a view count of the content instance for aplurality of other user devices.
 8. The method of claim 7, wherein theview count comprises a current view count, a cumulative view count, aview count by platform, or a combination thereof.
 9. A non-transitorycomputer-readable storage medium having one or more instructionsoperational on a client device, which when executed by at least onecomputer processor, cause the at least one computer processor to performoperations comprising: running, in an environment capable of runningthird-party applications, a first application in a first sandboxedvirtual operating environment of a user device, wherein the firstapplication comprises channel metadata unavailable to a secondapplication outside the first application; receiving a call, from thesecond application in a second sandboxed virtual operating environmentof the user device, for a module, wherein the module is a non-videoplayback module comprising graphic rendering logic; interceptingmetadata sent to the module; determining identifying information of acontent instance based on the intercepted metadata; generatingstatistics related to the content instance by analyzing the interceptedmetadata with respect to the content instance and at least one aggregatecontent identifier; forming an entertainment profile for a user of theuser device by associating the identifying information with a userprofile on the user device; and storing the determined identifyinginformation of the content instance, the statistics related to thecontent instance, the entertainment profile for the user, and a relationof the determined identifying information of the content instance to theentertainment profile for the user.
 10. The non-transitorycomputer-readable storage medium of claim 9, the operations furthercomprising rendering one or more of the channel metadata sent to themodule on a display screen using the module, prior to multimediaplayback of a received data stream.
 11. The non-transitorycomputer-readable storage medium of claim 9, the operations furthercomprising receiving a user selection of the content instance from aplurality of content instances, wherein the intercepted metadata is sentby the first application and is based on the content instance selectedby the user selection.
 12. The non-transitory computer-readable storagemedium of claim 9, the operations further comprising: determining, for aplurality of other user devices, at least one other content identifiercorresponding to the content instance, for at least one other userdevice of the plurality of other user devices, to form a plurality ofthe other content identifiers corresponding to the content instance;aggregating the plurality of the other content identifiers correspondingto the content instance, to create the at least one aggregate contentidentifier; and displaying the at least one aggregate contentidentifier.
 13. The non-transitory computer-readable storage medium ofclaim 12, wherein the at least one aggregate content identifier includesa most-watched program ranking based at least in part on a view-countstatistic, and wherein the most-watched program ranking is specific to aviewer demographic.
 14. The non-transitory computer-readable storagemedium of claim 9, wherein the channel metadata comprises at least oneof a title of the content instance, a director, a cast, or studioinformation, wherein the statistics related to the content instancecomprise a view count of the content instance for a plurality of otheruser devices, and wherein the view count comprises a current view count,a cumulative view count, a view count by platform, or a combinationthereof.
 15. A system, comprising: at least one computer configured toperform operations comprising: running, in an environment capable ofrunning third-party applications, a first application in a firstsandboxed virtual operating environment of a user device, wherein thefirst application comprises channel metadata unavailable to a secondapplication outside the first application; receiving a call, from thesecond application in a second sandboxed virtual operating environmentof the user device, for a module, wherein the module is a non-videoplayback module comprising graphic rendering logic; interceptingmetadata sent to the module; determining identifying information of acontent instance based on the intercepted metadata; generatingstatistics related to the content instance by analyzing the interceptedmetadata with respect to the content instance and at least one aggregatecontent identifier; forming an entertainment profile for a user of theuser device by associating the identifying information with a userprofile on the user device; and storing the determined identifyinginformation of the content instance, the statistics related to thecontent instance, the entertainment profile for the user, and a relationof the determined identifying information of the content instance to theentertainment profile for the user.
 16. The system of claim 15, theoperations further comprising rendering one or more of the channelmetadata sent to the module on a display screen using the module, priorto multimedia playback of a received data stream.
 17. The system ofclaim 15, the operations further comprising receiving a user selectionof the content instance from a plurality of content instances, whereinthe intercepted metadata is sent by the first application and is basedon the content instance selected by the user selection.
 18. The systemof claim 15, the operations further comprising: determining, for aplurality of other user devices, at least one other content identifiercorresponding to the content instance, for at least one other userdevice of the plurality of other user devices, to form a plurality ofthe other content identifiers corresponding to the content instance;aggregating the plurality of the other content identifiers correspondingto the content instance, to create the at least one aggregate contentidentifier; and displaying the at least one aggregate contentidentifier.
 19. The system of claim 18, wherein the at least oneaggregate content identifier includes a most-watched program rankingbased at least in part on a view-count statistic, and wherein themost-watched program ranking is specific to a viewer demographic. 20.The system of claim 15, wherein the channel metadata comprises at leastone of a title of the content instance, a director, a cast, or studioinformation, wherein the statistics related to the content instancecomprise a view count of the content instance for a plurality of otheruser devices, and wherein the view count comprises a current view count,a cumulative view count, a view count by platform, or a combinationthereof.